Technotools/Technotools (Chestnut CD-ROM)(1993).ISO/lang_oth/tm480/tmissue.exe/OVERVIEW.MAC

Text File | 1991-09-10 | 43KB | 1,380 lines

@vid
@macro idrop
@dim
@BBMENU blue,blue
@shadow bright,red,cyan
@drop under,offset 2
@col char,cyan,blue
@out cyan
@endm

@heading left,"Taskmaster OVERVIEW"
@head right,"Copyright FmP 1991"
@head centre,"Issue Menu"
@defaults bright,cyan,blue
@nf new
@col char,white,BLUE
@dim
@win line1,column1,depth3,width 78
New features in Taskmaster 4.80/SCR 4.70
@col char,CYAN,BLUE
@BBMENU CYAN,BLUE
{One }{Two }{Three }{Four }{Five }{Six }{Seven }
@BBhelp line3,column1,width 41,bright,white,blue
@help 'The new Taskmaster based installer'
@help 'Easier to implement Drop-Down menus/forms'
@help 'Bounce-bar Help - like this!'
@help 'Bounce-bar ACTION KEYS'
@help 'The Taskmaster ATTRIB command'
@help 'Easier to implement intersecting lines'
@help 'More flexible forms design re: fields'
@use 'Press <esc> to return to Main menu'
@end
@nf new_help
@col page,white,green
@col char,white,green
@bright
@border
@window line 7,column3,depth15,width74
@outline yellow

  This  menu  both describes and uses many new features to be  found  in
  Taskmaster version 4.80 and SCR version 4.70.

  Please  select topics in the normal way,  (press space if you are  not
  yet familiar with Taskmaster); as you do so you will notice that a one
  line help message is output on line 3.  Please note that all the texts
  for  this help facility are defined in the form and that the  facility
  requires no extra code in the application!

  When  you  have highlighted the required topic press 
.  This  will
  then DROP DOWN a screen of information.  When you have read the screen
  press return and the screen will be automatically restored.  This  all
  happens because there is a DROP directive in the form.
@end
@nf new01
@col char,cyan,blue
@WIN LINE0,COLUMN0,DEPTH11,WIDTH42
$idrop$

 New installer
@line
 Previous releases of shareware Taskmas-
 ter made  use of a BATCH file with  all
 this entails in terms of lack of  flex-
 ibility and poor user interface.   This
 was  a curious state of affairs  as  an
 installer  is an ideal application  for
 Taskmaster.   {x}
                       Press ,  or 

@end
@nf new02
@col char,cyan,blue
@WIN LINE0,COLUMN0,DEPTH15,WIDTH42
$idrop$

 Drop-Down menus and forms
@line
 Taskmaster menus like this one  automa-
 tically store the contents of that part
 of  the screen overwritten by the  text
 once  a selection has been  made.   The
 "shadow"  effect is also  automatically
 generated  in any desired colour.   The
 placement  of  the  drop-down  is  also
 automatic  (i.e.  below  the  currently
 highlighted  topic  if it will  fit  or
 aligned to the right hand side of   the
 screen and/or the bottom). {x}
                       Press ,  or 

@end
@nf new03
@col char,cyan,blue
@WIN LINE0,COLUMN0,DEPTH12,WIDTH42
$idrop$

 Bounce-bar Help
@line
 A  line of help related to  each  high-
 lighted  topic has long been a  feature
 of the Unix version of Taskmaster.  DOS
 users  can also benefit from this  lux-
 ury.   Please note that all  the  texts
 are  defined  as forms  source  and  no
 extra  code is needed in the  task   to
 implement the feature.  {x}
                       Press ,  or 

@end
@nf new04
@col char,cyan,blue
@WIN LINE0,COLUMN0,DEPTH19,WIDTH42
$idrop$

 Action keys
@line
 Taskmaster bounce-bar menus have always
 had a "First character search" capabil-
 ity.   It is sophisticated in that  two
 or more topics may start with the  same
 character  and still not confuse  Task-
 master.   "Instant"  bounce  bar  menus
 were  available  providing  that  first
 characters were not so duplicated.  The
 current version allows the provision of
 instant  bounce bar menus  by  allowing
 the  specification of  "action  charac-
 ters"  which appear highlighted  within
 the menu topics.  This highlighting can
 be considered an additional benefit  in
 its own right.{x}
                       Press ,  or 

@end
@nf new05
@col char,cyan,blue
@WIN LINE0,COLUMN0,DEPTH16,WIDTH42
$idrop$

 ATTRIB command
@line
 A  significant feature needed  by  many
 users  missing from DOS is the  ability
 to   set and read all  DOS  attributes.
 The DOS ATTRIB command only allows  you
 to change the READ-ONLY attribute.  The
 Taskmaster   ATTRIB  command  has   the
 advantage of being able to GET and  SET
 all DOS attributes and may even be used
 to hide directories and make them  vis-
 ible  again.  Now you can  easily  hide
 your  work  before you close  down  the
 machine! {x}
                       Press ,  or 

@end
@nf new06
@col char,cyan,blue
@WIN LINE0,COLUMN0,DEPTH10,WIDTH42
$idrop$

 The @LINE directive
@line
 The    above  line  is    automatically
 calculated and correctly intersects the
 existing  OUTLINE of the window.   Such
 screens as this have been possible  for
 6  years - now they are easier  to  de-
 sign. {x}
                       Press ,  or 

@end
@nf new07
@col char,cyan,blue
@WIN LINE0,COLUMN0,DEPTH13,WIDTH42
$idrop$

 The @MARKERS directive
@line
 In  data  capture forms,   before  this
 release  the field markers were  always
 fixed  and not optional.  You  may  now
 specify  that they not be used or  that
 markers   of  your  choice   be   used.
 Another  change is to allow  fields  to
 automatically  be filled with  dots  or
 underscores at run time.  See the  user
 interface menu for examples. {x}
                       Press ,  or 

@end

@nf doc_menu
@banner
@border
@bbmenu cyan,blue

             {LICENCE.FMP } Display End-user Licence Agreement
             {README.FMP  } Display Introductory notes on Taskmaster
             {SHARETM.FMP } Display Details of Taskmaster Issue files
             {VALIDATE    } Check availability of issued files
             {REPLICATE   } Copy issued files to a floppy diskette
             {QUIT        } Return to Main menu
@end
@nf errors
@col char,cyan,blue
@win line10,column14,depth3,width60,pattern 177

  The replication process failed.  The disc is incomplete.
@end

@nf nodest
@col char,cyan,blue
@win line10,column14,depth2,width60
Error: Failed to copy {01234567890123} to {01234567890123456789}
@end
@nf nosource
@col char,white,red
@win line10,column16,depth10,width47
@drop
@out black

 Error: File not available:
 {0123456789012345678901234567890123456789}

 Taskmaster is distributed in compressed form,
 the file will be found on the original issue
 disc.

 Operation abandoned - Press any key.
@end
@nf notshare
@col char,white,red
@win line10,column16,depth8,width45
@drop
@out black

 Error: You are currently running Taskmaster
 Professional.    You may not  use  this  to
 create  Shareware  discs.  Please  DISKCOPY
 your Unregistered Shareware issue diskette.

 Operation abandoned - Press any key...
@end
@nf registered
@col char,white,red
@win line10,column16,depth10,width45
@drop
@out black

 Error:  This option is only available  when
 OVERVIEW is being interpreted by an  unreg-
 istered copy of Shareware Taskmaster.

 Please DISKCOPY your Unregistered Shareware
 issue diskette.

 Operation abandoned - Press any key...
@end
@nf replicate_ok
@col char,white,blue
@dim
@win line10,column14,depth9,width40
@drop
@out black

 The replicate process was successful.

   Please label the disc:
   Shareware Taskmaster v4.80

 Please remember you may not make any
 charge for copies made by this means.
@end

@nf NO_COMSPEC
@border



      Warning: Reduced Facility level. 

     COMSPEC is currently set to {01234567890123456789}

     Taskmaster  requires access to the command processor (as  defined  in
     the environment variable COMSPEC) to load applications.  The  command
     processor  cannot be accessed at present - the  facilities  available
     through Taskmaster will therefore be limited.
@end
@nf NO_LIST
@border



      Warning: Reduced Facility level. 

     LIST.COM not present in:
     {                                                                    }

     This Public Domain  program is used in several places in  Taskmaster
     demonstrations to list files.    If you have a private copy  on  the
     PATH then this will be used instead,  otherwise  Taskmaster will not
     be able to list files.
@end

@nf drive
@col char,white,green
@bright
@win line10,column5,depth9,width70
@drop
@out black

 I  will check for files in:
 {0123456789012345678901234567890123456789012345678901234567890123}
 For any files not found there I will also look on the APPEND  list.
 If you installed only essential files you can expect some files  to
 be missing.

     Press any key to perform check... or <esc> to abort
@end
@nf repdrive
@acceptfk none
@range A,B
@col char,cyan,blue
@win line10,column14,depth1,width60
Replicate files to which drive?    [A] A or B
@end
@nf SMENU
@head centre,"Main Menu"
@col page,white,blue
@bright
@banner
@col char,cyan,blue
@dim
@border

@bbmenu cyan,blue
@key bright,white,blue
    {Introduction   } What is Taskmaster
    {End-User Menus } Menus that require no programming
    {Example Tasks  } Collection of example tasks
    {Online Manuals } Manuals for Taskmaster and SCR with Print facility
    {News           } Hot new features in Taskmaster
    {QUIT           } Exit Taskmaster

    Please make selection using <space> and then press 

@window line11,column10,depth11,width60
@outline cyan

  Menus are a key feature of Taskmaster. Although they can
  be  used intuitively,  to make full use of them you  may
  need  to access the plentiful help available  using  the
  following function keys:

          F1 = Full screen help for menus.
          F2 = 'One-line' help for menus.
          F3 = 'One-line' help for forms.
          F4 = 'Drop-Down' help on menus.
@use 'Select a topic and press 
 else press F1-F4'
@end
@nf MANMENU
@head centre,"Manuals Menu"
@col page,cyan,blue
@col char,white,blue
@bright
@banner
@col char,cyan,blue
@dim
@border

@bright
@bbmenu cyan,blue
    {TMMAN    } Loads the Taskmaster On-Line Manual
    {SCRMAN   } Loads the SCR On-Line Manual
    {PRINTMAN } Creates a printable file from Taskmaster Manual
    {PRINTSCR } Creates a printable file from SCR Manual

@win line8,column4,depth15,width72
@outline cyan,single

  Context  sensitive help is available on this menu.  Press  F1  after
  highlighting the option you are interested in.

  Pressing  
 will launch the currently highlighted application.
  When  the  application  launched has completed this  menu  will  re-
  appear.
@use 'F1=help on highlighted task, 
 run task. Press <esc> to exit menu'
@end
@nf TMMAN
@bright
@colour char,yellow,blue
@win line9,column5,depth13,width70
@col char,cyan,blue
 Help on TMMAN
@col char,yellow,blue
@bright

 TMMAN  is  the Taskmaster on-line manual.  It is  implemented  as  a
 separate  task.   Press 
  to invoke  it.  You  may  also  invoke
 it from the command line like this:

 TM TMMAN


 It  is  distributed  in  TMMANUAL.EXE  which  is  a  self-extracting
 archive.
@end
@nf SCRMAN
@bright
@colour char,yellow,blue
@win line9,column5,depth13,width70
@col char,cyan,blue
 Help on SCRMAN
@col char,yellow,blue
@bright

 SCRMAN  is  the  Screen Template Processor on-line  manual.   It  is
 implemented as a separate task.   Press 
 to invoke it.  You  may
 also invoke it from the command line like this:

 TM SCRMAN


 It  is  distributed  in  TMMANUAL.EXE  which  is  a  self-extracting
 archive.
@end
@nf PRINTMAN
@bright
@colour char,yellow,blue
@win line9,column5,depth13,width70
@col char,cyan,blue
 Help on PRINTMAN
@col char,yellow,blue
@bright

 This task takes the forms from TMMAN.OVR (as used by TMMAN.TSK)  and
 writes  their  screen images to a disc file (called  TMMAN.MAN)  for
 viewing or printing.

 You  can specify which sections are included.  The whole listing  is
 approximately 256k in size.

 Remember  that  TMMAN.MAN  is not as comprehensive  as  the  printed
 manual.  The format of the document is suitable for printing via  an
 IBM Graphics printer.
@end
@nf PRINTSCR
@bright
@colour char,yellow,blue
@win line9,column5,depth13,width70
@col char,cyan,blue
 Help on PRINTSCR
@col char,yellow,blue
@bright

 Like  PRINTMAN except this task takes the forms from SCRMAN.OVR  (as
 used  by SCRMAN.TSK) and writes their screen images to a  disc  file
 (called SCRMAN.MAN) for viewing or printing.  Requires 100k space.

 Remember  that  SCRMAN.MAN is not as comprehensive  as  the  printed
 manual.  The format of the document is suitable for printing via  an
 IBM Graphics printer.
@end
@nf EUMENU
@head centre,"End User Menus"
@col page,white,magenta
@col char,white,magenta
@bright
@banner
@border

@bbmenu white,magenta
    {CONFIG         } Set up application list for STANDARD
    {STANDARD       } Run applications set up by CONFIG
    {SMART          } Alternative END USER menu system

@win line8,column4,depth13,width72
@outline cyan,single

  STANDARD  and SMART are Taskmaster Tasks which  provide  simple  yet
  sophisticated  menu systems that require NO PROGRAMMING.   Like  any
  menu system,  to be useful they do need to be set up by a person who
  has a basic understanding of the applications, where they reside and
  how to invoke them.

  Please  note   that OVERVIEW invokes CONFIG and STANDARD with  a  /O
  flag  which  makes them behave in a special way (not  allowing  high
  security to be set).
@use 'F1=help on highlighted task, 
 run task. Press <esc> to exit menu'
@end
@nf CONFIG
@bright
@colour char,yellow,blue
@win line9,column5,depth11,width70

@col char,white,magenta
 Help on CONFIG task
@colour char,yellow,blue

 CONFIG.TSK  is  used  to setup details  of  applications  which  can
 subsequently be presented to the user by running STANDARD.TSK.  This
 task may be used by staff with no prior experience.  No  programming
 is required.
@end
@nf STANDARD
@colour char,yellow,blue
@bright
@win line9,column5,depth11,width70

@col char,white,magenta
 Help on STANDARD task
@colour char,yellow,blue

 This  task  displays a list of services to the  user  as  previosuly
 defined using CONFIG.TSK.  Both tasks are written in Taskmaster  and
 serve  to show how versatile the Taskmaster language is as  well  as
 providing a practical service.
@end
@nf SMART
@colour char,yellow,blue
@bright
@win line9,column5,depth11,width70

@col char,white,magenta
 Help on SMART task

@colour char,yellow,blue
 SMART.TSK  requires  that you know a username and password  to  gain
 entry  to  a menu of services.  If you don't have EUC  then a  dummy
 catalogue will have been provided containing some pre-set  usernames
 and passwords.  Note also that each user has associated a user group
 number and gaining entry by specifying a username and password  with
 a group number of 99 gives you special privileges.
@end
@nf intmenu
@head centre,"Introduction Menu"
@dim
@col page,black,cyan
@bright
@col char,white,blue
@banner
@col char,black,cyan
@dim
@border

@bbmenu black,cyan
@dim
    {Overview       } Quick look at features and applications
    {The issue disc } Details of files comprising Shareware Taskmaster
    {User interface } Forms, Menus, Windows
    {INTRO          } A Task explaining what Taskmaster is and who needs it
    {HELP           } Simple help system
    {QUIT           } Return to previous menu
@win line8,column4,depth14,width72
@outline black,single

  INTRO and HELP are separate applications (context sensitive help  is
  available for these - highlight and press F1 for more details).

  The   other  topics are built into this task.   These   topics   are
  general  in  nature, programmers should also look  at  the  examples
  menu.
@use 'Press <esc> to return to previous menu'
@end
@nf INTRO
@bright
@colour char,yellow,blue
@win line9,column5,depth12,width70

@col char,black,cyan
@dim
 Help on INTRO task
@bright
@colour char,yellow,blue

 If  you are still wondering what Taskmaster is or who needs it  this
 is perhaps the next place to look.

 INTRO is a separate task.  It is  an introduction  to  Shareware and
 Taskmaster, INTRO is implemented as a 'variable depth' menu system.

 This task is easily adapted to cover other subjects to provide  help
 for your applications.
@end
@nf HELP
@bright
@colour char,yellow,blue
@win line9,column5,depth12,width70

@dim
@col char,black,cyan
 Help on HELP task
@bright
@colour char,yellow,blue

 HELP.TSK  is an overview help system and describes basic  Taskmaster
 and SCR capabilities.

 Detailed help on Taskmaster can be found in TMMAN and detailed  help
 on  SCR can be found in SCRMAN; both are available via  the  On-line
 Manuals menu.
@end


@nf create_ovr
@acceptfk none
@logical
@col char,cyan,blue
@win line8,column4,depth13,width72
@drop
@outline cyan,single

 This  task cannot be run at present because it requires an OVR  file.
 These are created by SCR.   OVERVIEW can run SCR for you and then run
 the application.

 Create the OVR file ? [Y] (enter Y or N and press 
)
@end
@nf failed_ovr
@col char,white,red
@bright
@win line8,column4,depth13,width72
@drop
@outline cyan,single

  SCR  was  unable  to create the OVR file.   It returned  a  response
  indicating {0123456789012345678901234567}

  Please leave OVERVIEW and run SCR manually.  If there is  a  problem
  with  the  source file,  delete the TSK, MAC and OVR files  for  the
  application (e.g. for INTRO: DEL INTRO.*) and then  re-run  OVERVIEW
  which will run  the appropriate self extract archive to recreate the
  missing files.

  If problems persist, please re-install and try again.
@end

@nf overview
@col page,CYAN,BLUE
@border cyan,dim
@bbmenu white,BLUE
@col char,cyan,BLUE

 {TASKMASTER } is a subset of {PROTEAN },  Taskmaster  is  {PORTABLE } and  is
 available  {NETWORKED }. Taskmaster is an  {INTERPRETER }. It  reads  commands
 from  a file called a {TASK }. Taskmaster is in some ways like {BATCH } but is
 however far more sophisticated in many respects.
@col char,white,BLUE

 Taskmaster can display virtually any kind of data on your {VIDEO }.  Making
 few demands on the hardware, Taskmaster works well with basic {ADAPTERS }.

@col char,yellow,BLUE
@bright
 To  develop tasks an {EDITOR } is required.  Screens are processed by  {SCR }
 creating  an OVR file.  {TEMPLATES } (of which {MENUS } are a  special  kind)
 are taken from the OVR file by Taskmaster and displayed on the screen.

@dim
@col char,cyan,BLUE
 Taskmaster  code  is  {NEAR ENGLISH }. Taskmaster is designed  to  provide  a
 {USER-FRIENDLY } {FRONT-END } and its {FLEXIBILITY } means that it lends  itself
 to many other types of application. {RESTART }
@gon
@double_line
    7----------------------------------------------------------------------9
    0                                                                      0
    0   This is a menu.  Press 
 to see more detail of the first topic  0
    0   You may select topics in the usual manner,  the highlight will     0
    0   advance automatically. Press <esc> to exit.                        0
    0                                                                      0
    0                                                                      0
    2                                                                      2
@end
@nf Taskmaster
@col char,white,blue
@dim
@win line17,column5,depth6,width 70
 TASKMASTER
 Taskmaster  is implemented as a language,  it is in  fact  a  subset
 (i.e.  has some of the commands) of PROTEAN.   Technically it  is  a
 Job  Control  Language  or JCL.  It   particulary  lends  itself  to
 providing User Menus which can be made very easy to use if desired.
@end
@nf PROTEAN
@col char,white,blue
@dim
@win line17,column5,depth6,width 70
 PROTEAN
 The  PROTEAN language is unique to FmP and has been developed   over
 many years.  It offers unrivalled performance and is widely portable
 and runs on low cost hardware.
@end
@nf PORTABLE
@col char,white,blue
@dim
@win line17,column5,depth6,width 70
 PORTABLE
 PROTEAN is now available on MS-DOS, CDOS and Unix/Xenix.
@end
@nf Networked
@col char,white,blue
@dim
@win line17,column5,depth6,width 70
 NETWORKED
 Taskmaster and PROTEAN are available in networked versions  for  DR-
 NET on CDOS and Netware on MS-DOS.
@end
@nf interpreter
@col char,white,blue
@dim
@win line17,column5,depth6,width 70
 INTERPRETER
 Taskmaster code is not compiled, it is interpreted (in the  same way
 as is Basic).  PROTEAN does however have a CODE  GENERATOR facility.
@end
@nf TASK
@col char,white,blue
@dim
@win line17,column5,depth6,width 70
 TASK
 Tasks may be any length.  They may call other tasks. They  may  load
 any  MS-DOS  program,  if memory is scarce, Taskmaster   can  shrink
 down to 2k in size when it loads another program.
@end
@nf BATCH
@col char,white,blue
@dim
@win line17,column5,depth6,width 70
 BATCH
 Anything BATCH files can do Taskmaster can do better.  If you   have
 existing  BAT files then Taskmaster can encompass them   until  such
 time as you get around to re-writing them.
@end
@nf video
@col char,white,blue
@dim
@win line17,column5,depth6,width 70
 VIDEO
 Taskmaster  normally  works in 80 column, 25 line  mode.   It   will
 switch your video into a compatible mode when loading.   Most videos
 have several SCREEN PAGES, Taskmaster can make  full use of these.
@end
@nf adapters
@col char,white,blue
@dim
@win line17,column5,depth6,width 70
 ADAPTERS
 Taskmaster  works best with CGA  (or better) video  adaptors.   When
 invoked    with   the  /M flag it  will  work  perfectly  well  with
 monochrome (MDA)  adaptors as well.  It can also display screens  in
 40 column mode.
@end
@nf editor
@col char,white,blue
@dim
@win line17,column5,depth6,width 70
 EDITOR
 Any text editor which can read and write ASCII files is suitable for
 the  purpose.  I believe that some people are proficient  in  EDLIN,
 this can also be used.
@end
@nf SCR
@col char,white,blue
@dim
@win line17,column5,depth6,width 70
 SCR
 SCR  is the FmP Screen Template Processor - it takes all  DIRECTIVES
 and  text from a TSK or MAC file and creates an OVR file as  output.
 The  OVR  file is compact and contains sequences understood  by  the
 display manager which is part of the Taskmaster product.
@end
@nf TEMPLATES
@col char,white,blue
@dim
@win line17,column5,depth6,width 70
 TEMPLATES
 A Template is the generic name for a screen of data.  They are  very
 flexible and easy to develop.  They may even be developed separately
 from the Taskmaster source if required.
@end
@nf MENUS
@col char,white,blue
@dim
@win line17,column5,depth6,width 70
 MENUS
 Menus can take many guises, have you seen one like this before?
@end
@nf near English
@col char,white,blue
@dim
@win line17,column5,depth6,width 70
 NEAR ENGLISH
 Many  languages are inherently difficult to learn because  they  are
 cryptic,  Taskmaster is on the other hand verbose and so it is  easy
 to understand someone else's code (or your own in a few months).
@end
@nf User-Friendly
@col char,white,blue
@dim
@win line17,column5,depth6,width 70
 USER-FRIENDLY
 Users need not be DOS experts.  They need not even have access to  a
 DOS prompt.  They need not remember where applications  are kept and
 will  not  leave  files  lying  around  throughout  the    directory
 structure.   They  can be prompted to make backups  at   appropriate
 times,  Taskmaster can check that the correct discs are loaded...
@end
@nf Front-End
@col char,white,blue
@dim
@win line17,column5,depth6,width 70
 FRONT-END
 A  front-end is designed to interact with the operating system in  a
 sophisticated  way  whilst  interacting with you in  a  simple  way.
 Taskmaster can dramatically increase your productivity.
@end
@nf flexibility
@col char,white,blue
@dim
@win line17,column5,depth6,width 70
 FLEXIBILITY
 Taskmaster  is  so flexible that it lends itself to  many  kinds  of
 application.   Even  if you find you wish  to  develop  applications
 beyond  the  scope of Taskmaster you can  always  purchase  PROTEAN,
 which offers a further dimension in flexibility and performance.
@end
@nf TMENU
@head centre,"Examples Menu"
@col page,white,green
@col char,white,green
@bright
@banner
@col char,black,green
@dim
@border

@bright
@bbmenu white,green
          {WORDPROC }   {MENUONE }   {TMDEV }   {HOTEMENU }   {NATO   }
          {BROWSE   }   {WHEREIS }   {SWEEP }   {DIRECTOR }   {HVMENU }


@col char,black,green
@dim
@win line6,column4,depth17,width72
@outline black,single

  All these applications can be loaded directly from the system prompt
  using the command:

  TM NAME

@colour char,black,green

  TM  is  the  name of the Taskmaster interpreter  and  if  the  above
  command  were issued it would interpret NAME.TSK.
@colour char,black,green

  TMMAN and SCRMAN can also be invoked in this way.  Please note  that
  OVERVIEW invokes CONFIG and STANDARD with a /O flag which makes them
  behave in a special way (not allowing high security to be set).
@BBhelp line5,column9,width 62,bright,white,blue
@help 'WORDPROC: A wordprocessing harness'
@help 'MENUONE: Simple configurable menu with timeout'
@help 'TMDEV: A task development harness'
@help 'HOTEMENU: An example 2 level menu '
@help 'NATO: The NATO Phonetic Alphabet'
@help 'BROWSE: Mini file-manager type application'
@help 'WHEREIS: Shows use of Environment Variables'
@help 'SWEEP: Searches disc for files and then runs command on them'
@help 'DIRECTOR: Alternative directory display'
@help 'HVMENU: A safe cracking application. Horizontal/vertical menus'
@use 'F1=help on highlighted task, 
 to run it or <esc> for previous menu'
@bright
@end
@nf BROWSE
@bright
@colour char,yellow,blue
@win line7,column5,depth15,width70
@colour char,white,green

 Help on BROWSE task
@colour char,yellow,blue

 BROWSE.TSK allows you to browse through a set of upto 20 files at  a
 time to select one in order to perform basic actions on it  (delete,
 copy, move, protect etc).

 In addition up to 10 applications may be defined  (defaults  include
 LIST,  TM and  SCR) which appear  as  a menu from which a choice can
 be made.  Such defaults are stored in BROWSE.TM for future use.

 It is an example of the use of the Taskmaster DIR command which  can
 be used  to  return  the names (and update time/date) of  all  files
 meeting a specified filespec.  BROWSE may be used to view examples.
@end
@nf DIRECTOR
@bright
@colour char,yellow,blue
@win line7,column5,depth15,width70
@colour char,white,green

 Help on DIRECTOR task
@colour char,yellow,blue

 DIRECTOR.TSK  gets the DOS DIR command to place a list of  filenames
 into  a  file.  This file is then accessed as an ASCII file  by  the
 Taskmaster  RESTORE command.  The task takes parts of the  data  and
 reformats it and then displays it on the screen in colour.

 It is based on SWEEP task.
@end
@nf NATO
@bright
@colour char,yellow,blue
@win line7,column5,depth15,width70
@colour char,white,green

 Help on NATO task
@colour char,yellow,blue

 This  is  the only demonstration task that doesn't  require  an  OVR
 file.   It shows the use of the LOCATE and CURSOR commands and  also
 includes tables of variables.
@end
@nf SWEEP
@colour char,yellow,blue
@bright
@win line7,column5,depth15,width70
@colour char,white,green

 Help on SWEEP task
@colour char,yellow,blue

 Though  users  won't see it loaded, the MS-DOS  utility  ATTRIB   is
 pressed  into  service in this  task  which  can  build   customised
 BATCH  files  for you.   An  xample of use  would  be  to  find  all
 *.DOC files (in all directories) and use LIST to display them on the
 screen.   Another would be to find and delete all  *.BAK  files.
@end
@nf WHEREIS
@colour char,yellow,blue
@bright
@win line7,column5,depth15,width70
@colour char,white,green

 Help on WHEREIS task
@colour char,yellow,blue

 This  task examines the APPEND environment variable and uses  it  to
 determine the actual copy of a nominated file that an application is
 using.   It is intelligent enough to report the fact that APPEND  is
 not in the environment if this is the case.
@end
@nf wordproc
@colour char,yellow,blue
@bright
@win line7,column5,depth15,width70
@colour char,white,green

 Help on WORDPROC task
@colour char,yellow,blue

 WORDPROC.TSK  is  a harness for wordprocessor users.  It  saves  the
 names,  descriptions and edit details of a list of up to ten  files.
 Note  that copies of WORDPROC.TM may be present  in  any  number  of
 directories thus making the task more flexible.
@end
@nf HVMENU
@colour char,yellow,blue
@bright
@win line7,column5,depth15,width70
@colour char,white,green

 Help on HVMENU task
@colour char,yellow,blue

 This  is a bounce-bar menu example which has a Horizontal main  menu
 and  several  Vertical secondary menus.  It illustrates the  use  of
 TIMEOUTS and shows how the left and right arrow keys can be utilised
 to  cause an exit from a secondary menu,  a return to the main  menu
 and an immediate entry to the adjacent secondary menu.

 The  task  also uses the Taskmaster ENCODE command to check  if  you
 have the correct combination to open the SAFE.
@end
@nf HOTEMENU
@colour char,yellow,blue
@bright
@win line7,column5,depth15,width70
@colour char,white,green

 Help on HOTEMENU task
@colour char,yellow,blue

 This is another 2 level Bounce-Bar menu.  Note the use of background
 screen  colour via the "@colour page" directive.  The value  of  the
 display  system variable always contains the text of  the  currently
 highlighted  topic  after  bounce-bar  menu  display  -  even if  an
 alternative exit key is used (F1 for example).
@end
@nf TMDEV
@colour char,yellow,blue
@bright
@win line7,column5,depth15,width70
@colour char,white,green

 Help on TMDEV task
@colour char,yellow,blue

 This  is  a simple task development harness.  Intended  for  use  by
 application  developers.  Note that it won't let  you  edit  a  file
 until  the  filename has been confirmed.  This is  achieved  by  the
 "return 100" syntax variant which causes the menu to be re-displayed
 and   the  highlighted  topic  (as  determined  by  the   value   of
 CHOICE) being immediately selected.
@end
@nf MENUONE
@colour char,yellow,blue
@bright
@win line7,column5,depth15,width70
@colour char,white,green

 Help on MENUONE task
@colour char,yellow,blue

 This is a simple menu example that can save and restore data from  a
 datafile  called  MENUONE.TM.   It also shows  how  to  program  the
 Taskmaster   timeout  facility,  useful  in  secure   installations.
 Countdown restarts each time you hit a key.
@end
@nf NOT_AVAILABLE
@acceptfk none
@LOGICAL
@colour char,white,blue
@dim
@win line8,column4,depth13,width72
@drop
@outline white,double

  Sorry; the file{            } is not available.  It  is part  of  the
  Taskmaster  issue.  You may  recreate it  by  running {        }.
  This will create all files that are missing and allow you optionally
  to overwrite any that are already present.

  Do you want me to create the missing file(s) for you? [ ] Y or N

  I will place the file(s) in:
 {                                                                    }
@end
@nf NO_ROOM
@colour char,white,blue
@dim
@win line8,column4,depth13,width72
@drop
@outline white,double

  Sorry  the file{            } is not available.  It  is part  of  the
  Taskmaster  issue.  You may  recreate it  by  running {        } this
  will create all files that are missing and allow you  optionally  to
  overwrite any that are already present.

  Unfortunately  as you are running from a  floppy  drive  at  present
  space probabably won't permit this activity.
@end
@nf ISSUE_DISC
@acceptfk F10
@range A,B
@colour char,white,blue
@dim
@win line10,column6,depth8,width38
@drop
@outline white,double

 I need access to the Taskmaster
 Shareware issue  disc:
 Drive containing issue disc is [A]
 (enter A or B and press 
)
@line
 Press F10 to quit.
@end

@nf USER_INTERFACE
@col page,cyan,blue
@border

@bbmenu cyan,blue
                This is what we call a Bounce-Bar menu.
                Select option 1 to revert to Conventional.

@win line4,column26,depth12,width 28
@outline white

 {Conventional menu        }
 {Conversational commands  }
 {Simple Data capture form }
 {Simple (text only) form  }
 {Overlay form             }
 {Window form              }
 {Data capture form        }
 {New style data capture   }
@line
 {QUIT                     }

@win line16,column5,depth3,width 70
Please note that the underlying code is exactly the same whether  the
menu  is of the CONVENTIONAL or BOUNCE-BAR type.  ONLY the form  name
has been changed.  You may also press <esc> to quit this menu.
@bbhelp line22,column1,width78,bright,white,blue
@help ' Re-enter this menu using a "conventional menu" interface'
@help ' Display a message, then get a reply type interface'
@help ' Forms allow validation of data and an editing capability'
@help ' A form without fields is a simple form - however complex it looks!'
@help " Overlays don't clear the screen before being displayed"
@help ' Windows are defined using screen co-ordinates and may be patterned'
@help ' Forms allow multiple field data entry with editing capability'
@help ' Data capture with style changes implemented and function key control'
@help ' Return to the previous menu'
@end
@nf CONVENTIONAL
@menu opt9

                This is what we call a Conventional menu.
                Select option 1 to revert to Bounce-Bar.

                1.      Bounce-Bar menu
                2.      Conversational commands
                3.      Simple Data capture form
                4.      Simple (text only) form
                5.      Overlay form
                6.      Window form
                7.      Data capture form
                8.      New style data capture
                9.      QUIT

               [ ]

          NOTE: The effect of function keys on conventional menus
                is the same as entering a number and pressing 

@end
@nf goon
@acceptfk none
@logical
@col char,cyan,blue
@win line8,column9,depth 11,width 62
@out white

 Here  is a form containing a logical field (accepting only Y
 or  N  replies).   It  provides  an  easier  interface  than
 conversational commands as only a single command is required
 to execute it (PUT "FORMNAME"). Other attributes for example
 Colo
ur, reverse and flashing are also easier to apply to the
 message (not to mention graphics).
@double_line
         4555555555555555555555556
@line
 Are you ready to proceed ? [ ] (enter Y or N and press 
)
@bright
@end
@nf text
@draw
>C<
  Here is a simple form containing text only.

  By  default,  a form is preceded by a  clear   >R<
  screen  (unless  it  contains one  or   more       Even simple  forms
  WINDOWS or is designated as an OVERLAY.   By       can contain up  to
  default  when a form like this is  displayed       36 boxes like this
  the  prompt to be seen on the last  line  of                         >R<
  the screen is output automatically.  You may
@gon
  suppress it entirely or substitute your own.      7------8---------9
                                                    0 Semi 0 graphic 0
  Normally, a form is also followed by a clear      4------2-----8---2-9
  screen sequence; this may also be suppressed      0 characters 0 are 0
  if required.                                      4------8-----2-----2--9
                                                    0 also 0 child's play 0
  Simple forms can have text-insertion  fields      4----8-2---------8----3
  (not  to  be  confused  with  data   capture      0 to 0 implement 0
  fields).  To demonstrate text insertion here      1----2-----------3
  is the current date and time:

  The date today is: {dd mmm yyyy}
  and this form was displayed at {hh:mm}
                                             >C<
@end
@nf overlay
@overlay

















@draw
>1<
@colour char,white,red
  This  is  a simple overlay.  Like  a  normal
  form except that the initial clear screen is
  replaced by a home cursor sequence.         
                                             >1<

@end

@nf window
@colour char,cyan,blue
@win line6,column8,depth 15,width 55,pattern 177
@win line8,column24,depth 10,width 29
 This is a form containing 5
 windows.   Similar  to   an
 overlay  except  that   the
 placement  of the text   is
 determined  exactly   using
 a  @WINDOW  directive.  The
 area bounded by the  window
 is also cleared  to  spaces
 (or   a  nominated  pattern
 character).
@colour char,black,green
@win line19,column20,depth 3,width 52,pattern 179

  Here is another window with another pattern...
@colour char,white,red
@win  line9,column58,depth9,width 20
 To appreciate just
 how  easy this  is
 please look at the
 form called WINDOW
 in OVERVIEW.TSK...

 More   information
 on SCR is  located
 in SCRMAN.TSK.
@colour char,white,green
@bright
@win line2,column2,depth14,width 20
@out cyan

 Windows  may  have
 outlines which are
 automatically cre-
 ated by SCR to en-
 close   the   area
 bounded   by   the
 window.  See else-
 where in  OVERVIEW
 for  examples   of
 the user of  drop-
 down menus defined
 as windows.
@end

@nf DATACAPTURE
@time
@date
@string min10
@filename
@num min10,max 55
@logical
@border cyan

     The  following  fields  are validated automatically  according  to  the
     criteria specified when the form was designed.  The Task developer  can
     specify if fields are optional or mandatory.

     Use TAB, BACKTAB, HOME,  or  to move between fields. (F1 for help).
@draw
     >C<
                                time [hh:mm]
                                date [  /  /  ]
       string at least 10 characters [                    ]
                            filename [              ]
       num minimum 10 and maximum 55 [  ]
                    logical (Y or N) [ ]
                                                             >C<

@dim
     To  test the validation fill in the fields according to the legend  and
     press <return> - if one or more fields is invalid the appropriate  feet
     will flash and the cursor will be placed in the first failing field.   

     If you wish to abort the form instead of filling in the data  correctly
     simply  press  F2-F10 keys.  Press F1 to overlay a help form, other  F-
     Keys to quit. Function keys can be suppressed using @acceptfk.
@bright
@end
@nf DATACAPTURE2
@time
@date
@string min10
@filename
@num min10,max 55
@logical
@border cyan
@acceptfk f1,f10,esc

     With reference to the previous topic on the menu:

     You  may prefer to use alternative feet characters to define the  start
     an end of fields.  In this form we are using square brackets.  You  may
     even  decide to display no feet; in which case the option to  fill  the
     fields with full-stops or underscores (as seen below) will be welcome:

     Use TAB, BACKTAB, HOME,  or  to move between fields. (F1 for help)
@draw
@markers []
     >C<
                                time [-    ]
                                date [-       ]
       string at least 10 characters [.                   ]
                            filename [.             ]
       num minimum 10 and maximum 55 [. ]
                    logical (Y or N) [.]
                                                             >C<

@dim
     Note that the colour of the text being entered is user definable.
     Press F1 for help F10 or <esc> to quit (other F-Keys ignored)

@col char,white,red
@bright
     Taskmaster can save such data to a file or pass it to an application.
@end
@nf SAVE_SPACE
@head centre,'Saving Space'
@acceptfk none
@logical
@col char,white,blue
@bright
@banner
@col char,cyan,blue
@dim
@border

     The  processed  screens file {012345678901} was  created  successfully
     from  {012345678901}  by SCR.  The MAC file  is  therefore  no  longer
     required. I have checked and you have less than 100000 bytes of space
     on the logged drive.

     Shall I delete {012345678901} to save space? [N] Y or N

     P.S.  You  may  recreate it at will by  running  the  self-extracting
           archive.
@bright
@end
@nf missing_advice
@head centre,'Reinstating missing files'
@col char,white,blue
@bright
@banner
@col char,cyan,blue
@dim
@border

     The  validate option doesn't check for missing OVR files as these  can
     be  recreated by simply running SCR providing the relevant MAC or  TSK
     file is available.  Within OVERVIEW this is done automatically for you
     when you try to run the task.

     MAC  files are only required to create OVR files.  Once the  OVR  file
     has  been  created the MAC file can be deleted  (not  recommended  for
     tasks you develop for obvious reasons).  Whenever OVERVIEW creates  an
     OVR  from a MAC file it checks available disc space.  If this is  less
     than 100000 bytes it gives you the chance to delete the MAC file, this
     may explain its absence.

     Providing you have a copy of the Self Extracting Archives TMISSUE.EXE,
     TMMAN.EXE  and  TMEXAM.EXE you can re-create any issued file  that  is
     missing  by typing the name of the archive file at the system  prompt.
     You may run VALIDATE again to see which ARCHIVE you need to run.

     The  self extracting archives are not required for any  other  purpose
     and can be deleted if you want to save space.  We suggest performing a
     replicate first!
@end
@eof